cisco-cvp-ux
Delete PaymentMethod - TMF670 DELETE
Request
URL
http://[host]:[port]/cisco-cvp-ux/v1/{businessId}/paymentMethod/{id}
Common Parameters
Base URI parameters and headers are common to all the resources as part of payment-methods Biz API, listed below with details.
Base URI Parameter
Name | Type | M/O | Description |
---|---|---|---|
businessId | string | M | Business unit identifier. Example: PR |
id | string | M | Payment Method Id. Example: PAYMENT_99903 |
Headers
Name | Type | M/O | Description |
---|---|---|---|
X-Correlation-ID | string | M | This is a unique identifier for the current call chain that can be used to tie together log entries on multiple layers. Example: 644e1dd7-2a7f-18fb-b8ed-ed78c3F92c2b |
lob | string | M | The Line of Business Identifier currently available are: POSTPAID |
channelId | string | O | Channel to identify the business group. Ex: ivrB2C |
Security Headers
Name | Type | M/O | Description |
---|---|---|---|
client_id | string | M | Client Id value for Client Id Enforcement policy. Environment Specific Value. Eg: 6f0ed16a7b494d76b2d60e05bc3b3332 |
client_secret | string | M | Client secret value for Client Id Enforcement policy. Environment Specific Value, eg: e4CD4D43449846aA9D8Cb9c43fAd324a |
Body
{
"account": [
{
"id": "21514646-21516061",
"@type": "BillingAccount",
"relatedParty": [
{
"id": "19394109717",
"@type": "msisdn"
}
]
}
],
"relatedParty": [
{
"name": "IVR",
"@type": "channel"
}
]
}
Response
Possible response success
This section defines all the possible data structures received by the client and that must be considered satisfactory at the time of responding to the method.
Success Response
[ 200 ]
{
"status": 200,
"description": "payment method delete request received"
}